Fill gaps from assistant conversations: Entra SSO and multi-connector setup - #512
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Point to the Microsoft-specific section of the tenant setup guide instead of the top of the page, so readers land directly on the relevant instructions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…tors Okta, Google Workspace, OneLogin, JumpCloud, and PingOne all have the same connector-vs-SSO-login ambiguity as Entra ID. Add the same clarifying note, linked to each provider's specific SSO setup section. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Address two recurring assistant question themes by clarifying existing pages.
Changes
baton/microsoft-entra.mdx: added a note distinguishing the Entra ID connector (identity governance) from signing in to C1 with Entra ID SSO, linking to the tenant setup guide. Readers repeatedly conflated the two.product/admin/applications.mdx: extended "Should an app have multiple connectors?" to state that multiple connectors of the same type are supported (e.g., a second Okta connector for a second Okta org) and how to add one.Context
Assistant conversations in the past week showed users unable to find these answers on the affected pages. Other themes (API rate limits, HTTP connector poll interval, bulk-action/expiration-history endpoints) were skipped because the facts are not verifiable in the repo.